5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
- Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-17: Using Event Points

Establish PCF Range


This event point can be used to constrain the number of records that pass through a query. It is executed once, immediately after the Start of Query Execution event point. You can set range limitations either on the primary key or on alternate keys of the process control file, depending on the access path you choose. You can constrain the full key or a partial key. If this event point contains no statements, APPX will construct a range based upon the child constraints specified in the query's parent process. If no child constraints are specified in the parent, APPX uses the designer and end user selection criteria to establish the PCF range.

If this event point contains statements, even just comments, APPX assumes the designer wants control over the constraints and does not attempt to create its own constraints or use any child constraints specified in the parent. For example, if code exists in the event point to constrain records but this code is bypassed or disabled, no records will be selected.

If statements are entered in this event point, at minimum the range should be set by BEG AT and END AT statements, which should be followed by a BEG READ statement, then a GOSUB --- PROCESS QUERY RECORD statement that passes the record to the query, then an END READ statement. The predefined subroutine PROCESS QUERY RECORD calls the Pre-User Selection event point, evaluates the designer and end user selection criteria, and then calls the Post User Selection event point.

You may assign multiple constraints in this event point, and gather data from multiple files to establish your constraints. If the constraints overlap and produce a duplicate record situation, APPX will sense that and retain only one copy of the duplicate.

Application Design Manual                                         "Powered by Appx Software"

476

©2006 By APPX Software, Inc. All Rights Reserved